Micron Document

Identity
──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────

An identity is a cryptographic key that represents some kind of verifiable entity, be it a person, program, robot, computer, sensor or something else. It is the basis for all encrypted communication over Reticulum.cite-ref-1[1]

An identity can be used to create any number of destinations.

An identity consists of a 512-bit Curve25519 keyset:

• A 256-bit X25519 key for ECDH key exchanges
• A 256-bit Ed25519 key for signatures

Note: It is important to store an identity's private keys securely and privately. The loss of an identity's private key would mean the loss of control over its destinations.

Contents

Hash
Files

Hash

Identities are represented by a 16-byte hash derived from truncating a full SHA-256 hash of the identity's public keys.

identity_hash = truncate(SHA256(concatenate(public_encryption_key, public_signing_key)))

It is displayed as hexadecimal bytes, for example: bc7291552be7a58f361522990465165c

Files

In RNS, the identity of the default instance is stored in ~/.reticulum/storage/transport_identity. Other identities (such as network identity) are stored in the ~/.reticulum/storage/identities directory.

See also
References

cite-note-11. Identities, Manual. a8d24177d946de4f1f0a0fe1af9a1338:/page/blob.mu

Reticulum concepts
Identity